Search results for "software process improvement"

showing 4 items of 4 documents

Using organizational influence processes to overcome IS implementation barriers: lessons from a longitudinal case study of SPI implementation

2014

A fundamental tenet of the information systems (IS) discipline holds that: (a) a lack of formal power and influence over the organization targeted for change, (b) weak support from top management, and (c) organizational memories of prior failures are barriers to implementation success. Our research, informed by organization influence, compellingly illustrates that such conditions do not necessarily doom a project to failure. In this paper, we present an analysis of how an IS implementation team designed and enacted a coordinated strategy of organizational influence to achieve implementation success despite these barriers. Our empirical analysis also found that technology implementation and …

Information managementKnowledge managementlongitudinal case studyComputer sciencebusiness.industrybarriersIS implementation; longitudinal case study; organizational influence processes; software process improvement; barriersInformation technologyLibrary and Information SciencesBusiness modelManagement information systemsIS implementationAccounting information systemInformation systemSoft systems methodologyStrategic information systemorganizational influence processessoftware process improvementbusinessInformation SystemsEuropean Journal of Information Systems
researchProduct

A root cause analysis method for preventing erratic behavior in software development: PEBA

2019

Measures taken to prevent faults from being introduced or going undetected can secure development of highly reliable software systems. One such measure is analyzing root causes of recurring faults and preventing them from appearing again. Previous methods developed for this purpose have been reactive in nature and relied heavily on fault reporting mechanisms of ogranizations. Additionally, previous efforts lack a defined mechanism for innovating corrective actions. In this study, we strive to complement the existing methods by introducing a proactive and qualitative method that does not rely on fault data. During the course of the research, in addition to an extensive literature search, an …

Root (linguistics)Computer sciencefault removalohjelmistotekniikka0211 other engineering and technologiesfault preventionContext (language use)quality assurance02 engineering and technologyFault (power engineering)Industrial and Manufacturing EngineeringField (computer science)Software systemsoftware process improvementSafety Risk Reliability and Quality021110 strategic defence & security studies021103 operations researchbusiness.industrytietokoneohjelmatSoftware developmentProactivitysoftware reliabilityRisk analysis (engineering)root cause analysisohjelmistokehitysRoot cause analysisbusinessReliability Engineering & System Safety
researchProduct

An Information Systems Design Product Theory for Software Project Estimation and Measurement Systems

2009

There is relatively little research on software Project Estimation and Measurement Systems (PEMS). Commercial PEMS vary in functionality and effectiveness. Their intended users thus do not know what to expect from PEMS and how to evaluate them. This paper creates an information system design product theory for the class of PEMS that prescribes the meta-requirements, the meta-design, and applicable theories for all products within the class. Meta-requirements and the meta-design are derived from the project estimation and measurement literature, experiences obtained during more than ten years of empirical work in Finnish Software Measurement Association, and a commercially available PEMS.

functional size measurementorganizational learningoutsourcingknowledge managementsoftware process improvementsoftware project estimation and benchmarking
researchProduct

An Information Systems Design Theory for Integrated Requirements and Release Management Systems

2009

High-tech companies need to collect and analyze requirements and allocate them to appropriate product releases in market-driven product development. Development activities are typically scattered across multiple sites and involve multiple partners in different countries, complicating requirements and release management. Flexible, scalable, and secure groupware-based support for the activities provides substantial payoffs. Yet, the extant literature provides little theoretical guidance for designing and using requirements and release management systems in multi-site, multi-partner environments. This article develops the meta-requirements and a meta-design of an information systems design the…

requirements managementglobal sofware developmentinformation systems design theoryknowledge managementrelease managementsoftware process improvement
researchProduct